1. AtomicProvider now reactively subscribes to rpcConfigStore so changing custom RPC URLs triggers a rerender and polling uses fresh URLs.

2. HTLCClient.getSolverLockDetails restored cross-node agreement check: queries all nodes in parallel and requires matching lock details before accepting, preventing false lock detection from stale/faulty nodes.

3. TON client now respects network-aware RPC configuration: createTonClient(network) is called by getTONDetails and commitTransactionBuilder instead of using a hardcoded singleton.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

- Updated AtomicProvider to include destinationRedeemTx in the htlcStatus calculation for improved accuracy.
- Replaced NodeResolver class with a standalone resolveNodes function for better clarity and performance in resolving RPC nodes.
- Enhanced useSolverLockPolling to implement consensus verification across multiple nodes, ensuring consistent lock details are returned.
- Added validation for custom RPC URLs in the rpcConfigStore to prevent invalid URLs from being used.

These changes improve the reliability and maintainability of the RPC handling and polling mechanisms.

…ication in useSolverLockPolling

- Adjusted the timeout duration in AtomicProvider from 3 minutes to 2 minutes for manual claim requirements.
- Added useEffect in useSolverLockPolling to reset consensus verification state when hashlock changes, improving polling accuracy.

These changes enhance the responsiveness and reliability of the HTLC handling logic.

…tion effect

- Modified the useEffect in useSolverLockPolling to reset consensus verification state when both hashlock and nodeUrls change, improving the accuracy of polling behavior.

This change enhances the responsiveness of the HTLC handling logic by ensuring that the polling mechanism reacts to updates in node URLs.